<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
    <channel>
        <title>Business Analyst Community &amp; Resources | Modern Analyst</title> 
        <link>https://modernanalyst.com</link> 
        <description>RSS feeds for Business Analyst Community &amp; Resources | Modern Analyst</description> 
        <ttl>60</ttl> <item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1715/What-Business-Analysts-Can-Learn-from-Competitive-Sports-The-Power-of-Consistency.aspx#Comments</comments> 
    <slash:comments>6</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1715</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1715&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>What Business Analysts Can Learn from Competitive Sports: The Power of Consistency</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1715/What-Business-Analysts-Can-Learn-from-Competitive-Sports-The-Power-of-Consistency.aspx</link> 
    <description>While my co-workers know me as a manager of Business and Systems Analysis, others know me as a Triathlete (A triathlon is multi-sport event involving the completion of three continuous and sequential endurance events; most commonly swimming, bicycling, and running).&amp;#160; It was while reading a recent article about Triathlon that I began to draw a strong parallel between achieving career goals as a business analyst and achieving goals as a triathlete.&amp;#160; </description> 
    <dc:creator>cadams5</dc:creator> 
    <pubDate>Tue, 22 Mar 2011 04:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1715</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/574/Security-Tool-Chest-Checklists.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=574</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=574&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Security Tool Chest: Checklists</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/574/Security-Tool-Chest-Checklists.aspx</link> 
    <description>Every career has a set of skills that one needs to do their job, and a set of tools to carry out the various tasks required to display their skills. Same is the case for the analyst involved in security assessment...&amp;nbsp;I have chosen the all mighty checklist as my tool of choice for this article.
</description> 
    <dc:creator>cadams5</dc:creator> 
    <pubDate>Sun, 05 Oct 2008 07:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:574</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/123/The-Pros-and-Cons-of-Use-Case-Diagrams.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=123</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=123&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Pros and Cons of Use Case Diagrams</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/123/The-Pros-and-Cons-of-Use-Case-Diagrams.aspx</link> 
    <description>
In the Unified Modeling Language (UML), use cases are visually represented as ellipses. However, in spite of its popularity and size, UML has little of practical use to offer modelers beyond this simple iconic representation. Trying to capture and present requirements using just use case diagrams can often render the otherwise useful technique of use cases almost useless.
Practitioners are often drawn to expressing their intent by overworking the limited use case diagram notation, losing readers in a myriad of bubbles muddled together with obscure relationships and microscopic text. This article takes a step back to examine the pitfalls and recommend a more balanced and restrained approach.

Author: Kevlin Henney</description> 
    <dc:creator>cadams5</dc:creator> 
    <pubDate>Sat, 29 Sep 2007 17:46:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:123</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7/Analysis-and-Design-Considered-Harmful.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=7</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>&quot;Analysis and Design&quot; Considered Harmful</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7/Analysis-and-Design-Considered-Harmful.aspx</link> 
    <description>This article describes a common pitfall of thinking of analysis and design together as a single process, and highlights the need to treat analysis and design as two separate processes. The author, points out that much of the UML standard, as it is explained today, is described in terms of design artifacts rather than analysis artifacts.
Author: Conrad Weisert</description> 
    <dc:creator>cadams5</dc:creator> 
    <pubDate>Wed, 01 Aug 2007 17:14:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:7</guid> 
    <enclosure url="http://www.idinews.com/analysisDesign.html" length="114" type="text/html" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5/Implicit-Data-Dictionaries-are-Dangerous.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Implicit Data Dictionaries are Dangerous!</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5/Implicit-Data-Dictionaries-are-Dangerous.aspx</link> 
    <description>Describes the difference between a data dictionary and an implicit data dictionary and why an implicit data dictionary (or no data dictionary at all) may spell trouble for your project. Can data dictionaries be used with UML Use Cases or an XP methodology?
Author: Conrad Weisert</description> 
    <dc:creator>cadams5</dc:creator> 
    <pubDate>Wed, 01 Aug 2007 16:34:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5</guid> 
    <enclosure url="http://www.idinews.com/implDataDict.html" length="114" type="text/html" />
</item>

    </channel>
</rss>